---
title: npm Logos and Usage
edit_on_github: false
redirect_from:
  - /policies/trademark/
---

This policy describes npm logos and trademarks and how you may use them. For information on what to do if someone infringes a trademark of _yours_ with a confusing package name, see the [Disputes policy][disputes].

## What is npm?

The npm project contains two main parts:

1. The npm client. It is a command line tool to install and publish packages.
2. The npm registry service. npm, Inc. runs the registry as a free (as in beer) public service for anyone wanting to publish an open source package and for anyone to install an open source package.

## Why npm, Inc. has a logo policy

"npm" and the npm logos are trademarks owned by npm, Inc. We have developed this policy to make it clear how other businesses and projects can (and cannot) use the npm name and logos.

## General rules

- When referring to the npm software in body text, the first usage should be followed by a generic term such as "package manager," "services" or "client" to provide context.
- "npm" should never be used or explained as an acronym.
- When referring to the npm public registry, please follow npm with the word "registry" or the phrase "public registry".
- When referring to a private registry for npm packages, please describe it as "private registry for npm packages" or a "proxy of the npm registry".
- References to the owner of the npm client software and the operator of the npm public registry should be to "npm, Inc."
- Any materials referring to npm should include the following notice in the footer or wherever you may have your own trademark notice: "npm is a registered trademark of npm, Inc."

## Nominative use - No need to type ™ on Twitter&reg;

"Nominative" or "referential" use means to refer to something or someone else by their trademark. So it's perfectly OK to use "npm" to refer to npm, Inc., the npm client, npm code, and the npm public registry. A referential use is generally going to be in a sentence or sentence fragment, like "first install the npm client," or in a book or article title. The use should not be attention-getting or potentially misperceived as suggesting "npm" is your own name, project, product or services.

It is not a referential use to incorporate the letters "npm" or any of the npm logos in the name or logo for your own company or its projects, products, services or social media handles.

If you need to use "npm" to indicate compatibility, you should use "npm" after your own product or service name and an accurate preposition:

- Pink Unicorn Consulting Ltd. services <strong>for</strong> npm
- Purple Unicorn Inc. private registry server <strong>compatible with</strong> the npm client
- Kappa, a hierarchical proxy <strong>of</strong> the npm registry

You need to ask for permission for any uses not described. When in doubt about your use of the npm name or logo, please contact [npm, Inc.](https://www.npmjs.com/contact) for clarification.

## Requesting permission

We like to make it easy for anyone to use the npm name or logo for community-oriented efforts that help spread and improve npm. We are therefore likely to grant permission to use the npm name and logo in the following ways:

- For projects where:
  - The primary purpose of your project is to promote the spread and improvement of the npm client software or the npm registry service.
  - Your project is non-commercial in nature (it can make money to cover its costs or contribute to non-profit entities, but it cannot be run as a for-profit project or business).
  - Your project neither promotes nor is associated with entities that currently fail to comply with the Artistic License 2.0 under which npm is distributed, or which are in violation of this policy.
- For a user group name where:
  - The main focus of the group is the software.
  - Any software or services the group provides are without cost.
  - The group does not make a profit.
  - Any charge to attend meetings are to cover the cost of the venue, food and drink only.

Any other requests are not likely to be granted licenses, but feel free to [ask](https://www.npmjs.com/contact).

## The npm Logos

Our npm Logos are very recognizable and deserve special treatment. In short, the npm logos represent only npm and should not be used to represent your products. The npm Logos signify us, or a special relationship with us, and you may use them only with our permission. Since the goal is to avoid confusion about you being us, or your relationship with us, context counts. We will [consider requests](https://www.npmjs.com/contact) on a case-by-case basis.

## The npm Wombat Mascot

Like the npm Logo, the npm Wombat graphic is a very recognizable part of the npm brand, and signifies a special relationship with the npm project, service, or company. It should never be used except with explicit written permission. We will [consider requests](https://www.npmjs.com/contact) on a case-by-case basis.

Please be advised that the Wombat and the logos generally may **not** be used to refer to the project, service, or company in a nominative sense, as any usage will almost always imply a special relationship with npm.

## Changes

This is a living document and may be updated from time to time. Please refer to the [git history for this document](https://github.com/npm/documentation/blob/main/content/policies/logos-and-usage.mdx) to view the changes.

## License

Copyright &copy; npm, Inc.

This document may be reused under a [Creative Commons Attribution-ShareAlike License](https://creativecommons.org/licenses/by-sa/4.0/).

[disputes]: /policies/disputes
